OSDOCS [Dual stream/Image Stream] Support two major versions of RHEL CoreOS in a single OCP release & cluster#109617
Conversation
openshift-ci
Bot
added
the
size/L
|
🤖 Thu May 14 18:53:25 - Prow CI generated the docs preview: |
|
@pablintino PTAL |
|
|
||
| By default, {op-system} 9.x is installed on {product-title} clusters starting with 4.14. | ||
|
|
||
| At any time, you can revert the cluster back to {op-system} 9.x, if needed. |
There was a problem hiding this comment.
@pablintino Are we officially supporting it?
There was a problem hiding this comment.
I think this is gonna depend on the target version of this doc. If it's for 5.0, yes, is not going to be supported, and tbh, I doubt we will support similar roll-backs anytime soon. The expectation is that if something goes wrong on a pool that is transitioning is to recreate the node after the stream is back ot the old one.
There was a problem hiding this comment.
Jira for tracking this issue: https://redhat.atlassian.net/browse/OSDOCS-19639
| - Name: Image mode for OpenShift | ||
| File: mco-coreos-layering | ||
| Distros: openshift-enterprise,openshift-origin | ||
| - Name: OpenShift Container Platform image streams |
There was a problem hiding this comment.
I think we need to ask @yuqi-zhang or Mark about the official name. Image Stream may be confusing as it's something that has existed in OCP for a long time and has almost zero relation with OS Image Streams, that is the name we have been using lately.
There was a problem hiding this comment.
I have "Setting the RHCOS version in a cluster" as the title of the assembly. Does that work better?
There was a problem hiding this comment.
I see based on the docs so far, this is more so documenting RHEL10, so I guess my question would be whether you intend to expand this to cover the feature generally speaking (For example, we'll possibly have an NVIDIA stream eventually).
I'd defer to @marrusl for specifics, but I think offhand if we want this to be generic, it'd be something like "RHEL CoreOS Stream Selection"
|
|
||
| By default, {op-system} 9.x is installed on {product-title} clusters starting with 4.14. | ||
|
|
||
| At any time, you can revert the cluster back to {op-system} 9.x, if needed. |
There was a problem hiding this comment.
I think this is gonna depend on the target version of this doc. If it's for 5.0, yes, is not going to be supported, and tbh, I doubt we will support similar roll-backs anytime soon. The expectation is that if something goes wrong on a pool that is transitioning is to recreate the node after the stream is back ot the old one.
mburke5678
force-pushed
the
mco-image-streams
branch
from
54bf381 to
b34d2b0
Compare
mburke5678
added
the
merge-review-needed
|
/retest |
mburke5678
changed the title
|
/label merge-review-in-progress |
openshift-ci
Bot
added
the
merge-review-in-progress
|
Just so I don't forget to mention it when I submit my review, remember to squash your commits before merging. |
bergerhoffer
left a comment
bergerhoffer
left a comment
There was a problem hiding this comment.
Just a few bits of feedback, but nothing major. LGTM (other than squashing commits)!
bergerhoffer
removed
merge-review-in-progress
…CP release & cluster
mburke5678
force-pushed
the
mco-image-streams
branch
from
30221cc to
f70544b
Compare
|
/retest |
|
@mburke5678: all tests passed! Full PR test history. Your PR dashboard. DetailsInstructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here. |
|
/cherrypick enterprise-4.22 |
|
@mburke5678: new pull request created: #111717 DetailsIn response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. |
8 participants
https://redhat.atlassian.net/browse/OSDOCS-17712
This is based on https://docs.google.com/document/d/1JMEL7hXT2j0nqGJN28YbkMTPY7qjrHFCtDUUFYStaw0/edit?pli=1&tab=t.0#heading=h.e6spuer7bqoe.
Link to docs preview:
Macnine Configuration -> Setting the RHCOS version in a cluster
QE review: